Skip to content

ci: refresh lockfiles on an unchanged release PR - #483

Merged
chrispader merged 1 commit into
mainfrom
ci/refresh-open-release-pr
Nov 10, 2026
Merged

chrispader merged 1 commit into
mainfrom
ci/refresh-open-release-pr

Conversation

@chrispader

Copy link
Copy Markdown
Member

The release PR's lockfiles are only updated on pushes where Release Please changes the PR. When the PR is already current, Release Please returns nothing, so the lockfile job is skipped. #479 is stuck that way: it is at 10.3.0, but the lockfile job failed on the push that set that version, and later pushes skip it, so its checks keep failing.

When Release Please returns no PR, the push run now looks up the open release PR by its autorelease: pending label and runs the lockfile job on that branch. The job only commits files that changed.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
react-native-nitro-sqlite Ready Ready Preview Nov 10, 2026 11:42am UTC

Request Review

@chrispader
chrispader merged commit db41e07 into main Nov 10, 2026
3 of 4 checks passed

This branch was successfully deployed

1 active deployment
Preview — 498071a2 Deployed Nov 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant